Computer-based systems involving enhanced one-time passcode (otp) messaging and methods of use thereof

ABSTRACT

Systems and methods for enhanced OTP messaging, comprising: receiving a request from an application executing on a computing device of a user; generating the supplemental information based on the request; segmenting the supplemental information into a first part of the supplemental information and a second part of the supplemental information; transmitting the first part of the supplemental information to the computing device of the user via a first communication channel to another app executing on the computing device of the user; instructing the another app to allow the user to utilize one or more graphical user interface (GUI) elements of a GUI of the another app to transfer the first part of the supplemental information to the app; and transmitting the second part of the supplemental information to the computing device of the user via a second communication channel so as to provide the supplemental information to the app.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever. The following notice applies to the software and dataas described below and in drawings that form a part of this document:Copyright, Capital One Services, LLC., All Rights Reserved.

FIELD OF TECHNOLOGY

The present disclosure generally relates to improved messaging, improvedchallenge based authentications, improved computer-based platforms orsystems, improved computing components and devices and/or improvedcomputing methods configured for one or more novel technologicalapplications involving enhanced one-time passcode (OTP) messages.

BACKGROUND OF TECHNOLOGY

A computer network platform/system may include a group of computers(e.g., clients, servers, computing clusters, cloud resources, etc.) andother computing hardware devices that are linked and communicate viasoftware architecture, communication applications, and/or softwareapplications associated with electronic transactions, data processing,and/or account management.

SUMMARY OF DESCRIBED SUBJECT MATTER

In some embodiments, the present disclosure provides various exemplarytechnically improved method for enhancing OTP based authentication,comprising operations such as:

-   -   receiving, by a processor, a request from an application (app)        executing on a computing device of a user, the request being        transmitted in response to the user operating the app to a stage        where supplemental information is required to further operate        one or more functionalities of the app;    -   generating, by the processor, the supplemental information based        on the request;    -   segmenting, by the processor, the supplemental information into        a first part of the supplemental information and a second part        of the supplemental information;    -   transmitting, by the processor, the first part of the        supplemental information to the computing device of the user via        a first communication channel to another app executing on the        computing device of the user;    -   instructing, by the processor, the another app to allow the user        to utilize one or more graphical user interface (GUI) elements        of a GUI of the another app to transfer the first part of the        supplemental information to the app;    -   receiving, by the processor, an indication of the transferring;        and    -   transmitting, by the processor based on the indication of the        transferring, the second part of the supplemental information to        the computing device of the user via a second communication        channel so as to provide the supplemental information to the        app.

In some embodiments, the present disclosure provides various exemplarytechnically improved method for enhancing OTP based authentication,comprising operations such as:

-   -   receiving, by a server, a request from an application (app)        executing on a computing device of a user to a server, the        request being transmitted in response to the user operating the        app to a stage where supplemental information is required to        further operate one or more functionalities of the app;    -   determining, by the server, the supplemental information based        on the request;    -   anonymizing, by the server, a portion of the supplemental        information into unreadable format;    -   transmitting, by the server, the unreadable portion of the        supplemental information in a message to a messaging app        executing on the computing device;    -   detecting, by the server, that the user uses one or more        graphical user interface (GUI) elements of a GUI of the        messaging app to transfer the unreadable portion of the        supplemental information to the app; and    -   causing, by the server, in response to the detecting, to provide        a remaining part of the supplemental information to the app.

In some embodiments, the present disclosure also provides exemplarytechnically improved computer-based systems, computer-implementedmethods, and computer-readable media, including media implemented withand/or involving one or more software applications, whether resident oncomputer devices or platforms, provided for download via a server and/orexecuted in connection with at least one network such as via a webbrowser application, that include or involves features, functionality,computing components and/or steps consistent with those set forthherein.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present disclosure can be further explainedwith reference to the attached drawings, wherein like structures arereferred to by like numerals throughout the several views. The drawingsshown are not necessarily to scale, with emphasis instead generallybeing placed upon illustrating the principles of the present disclosure.Therefore, specific structural and functional details disclosed hereinare not to be interpreted as limiting, but merely as a representativebasis for teaching one skilled in the art to variously employ one ormore illustrative embodiments.

FIG. 1 is a block diagram of an exemplary system and/or platforminvolving features of challenge based authentications via enhancedone-time passcode (OTP) messaging, consistent with exemplary aspects ofcertain embodiments of the present disclosure.

FIG. 2 is a block diagram of an exemplary challenge based authenticationsystem via enhanced OTP messaging, consistent with exemplary aspects ofcertain embodiments of the present disclosure.

FIGS. 3A-3C are diagrams of certain illustrative aspects of exemplarygraphical user interfaces (GUIs) enabling a user to perform challengebased authentication via enhanced OTP messaging, consistent withexemplary aspects of certain embodiments of the present disclosure.

FIG. 4A is a flowchart depicting an exemplary method for providingchallenge based authentications via enhanced OTP messaging, consistentwith exemplary aspects of certain embodiments of the present disclosure.

FIG. 4B is a flowchart depicting another exemplary method for providingchallenge based authentications via enhanced OTP messaging, consistentwith exemplary aspects of certain embodiments of the present disclosure.

FIG. 5 is a block diagram depicting an exemplary computer-based systemand/or platform, in accordance with certain embodiments of the presentdisclosure.

FIG. 6 is a block diagram depicting another exemplary computer-basedsystem and/or platform, in accordance with certain embodiments of thepresent disclosure.

FIGS. 7 and 8 are diagrams illustrating two exemplary implementations ofcloud computing architecture/aspects with respect to which the disclosedtechnology may be specifically configured to operate, in accordance withcertain embodiments of the present disclosure.

DETAILED DESCRIPTION

Various detailed embodiments of the present disclosure, taken inconjunction with the accompanying figures, are disclosed herein;however, it is to be understood that the disclosed embodiments aremerely illustrative. In addition, each of the examples given inconnection with the various embodiments of the present disclosure isintended to be illustrative, and not restrictive.

Throughout the specification, the following terms take the meaningsexplicitly associated herein, unless the context clearly dictatesotherwise. The phrases “in one embodiment” and “in some embodiments” asused herein do not necessarily refer to the same embodiment(s), thoughit may. Furthermore, the phrases “in another embodiment” and “in someother embodiments” as used herein do not necessarily refer to adifferent embodiment, although it may. Thus, as described below, variousembodiments may be readily combined, without departing from the scope orspirit of the present disclosure.

As explained in more detail, below, enhanced messages, systems, andmethods for providing challenge based authentications involving enhancedOTP messaging are disclosed. According to some aspects, with exemplaryenhanced OTP messaging, OTP information (e.g., supplemental information)may comprise at least a first part and a second part, the first part andthe second part being transmitted via distinct messaging apps ormessaging channels to a computing device of a user awaiting the OTPinformation to complete an authentication process with an app, a webbrowser page, etc. (collectively, an app) executing on the computingdevice. Further, the second part may only be transmitted to thecomputing device upon the first part having been received at thecomputing device and transferred to the app. According to some otheraspects, exemplary enhanced OTP messaging may have at least part of theOTP information anonymized into an unreadable format for transmission tothe computing device of the user. This way, the OTP information, whenreceived and displayed in a message at a messaging app executing on thecomputing device of the user, may not be readable, visually accessible,audibly accessible, or otherwise comprehensible to the user. In thisembodiment, the transfer of the OTP information to the app is restrictedto operations provided at the messaging app (or system level setting)such that, for example, the conventional way of the user reading out orwriting down the OTP displayed in the messaging app for manual keyinginto the app is not supported. One exemplary way to restrictivelytransfer the OTP information to the app may be configured such that themessaging app, upon detecting the unreadable format of the OTPinformation and the message being transmitted from an OTP server,displays an operable GUI element on the messaging app to allow the OTPinformation to be transferred to the app upon the user's selection ofthe GUI element.

Further according to some other aspects, exemplary enhanced OTPmessaging may configure part of the OTP message with a security token(e.g., secret knowledge shared between the user and the app server/OTPserver) such that the OTP messages may be deemed as being transmittedfrom authorized app server or OTP server only when the security token ispresent in or displayed along with the OTP message. Augmented with thesecurity token, the disclosed technology provides further enhancedsecurity measures to safeguard against frauds involved withcommunicating sensitive information such as OTP.

Still further according to some other aspects, exemplary enhanced OTPmessaging may customize the content and/or the format of OTP messagesusing the knowledge about the user's computing device and messaging app,as well as using a machine learning model trained with demographic dataand behavioral data associated with an individual user or a group ofuser. Empowered with the insight and intelligence about the user, theuser's contexts, similar users, user's computing device's capabilitiesand functionalities, the format, and content of the message may becustomized to better appeal to the user, thereby contributing to ahigher completion rate with regard to challenge based authenticationinvolving the supplemental information.

While challenge based authentications and OTP information are usedherein connection to illustrate various aspects of the disclosure, itshould be understood that the disclosed technology pertains to anyrelevant application or process with which any type of informationsupplemental to their operations is required in a more secure and lessfraud susceptible manner. By way of non-limiting examples, given theimprovement that supplemental information is obfuscated into anunreadable format (or not displayed at all), the real content of thesupplemental information is no longer subject to phishing activities(voice phishing, etc.) as the information can only be transferred in anautomated cross-app fashion that is triggered by the user.

Various embodiments disclosed herein may be implemented in connectionwith one or more entities that provide, maintain, manage, or otherwiseoffer any services via enhanced messaging. In some embodiments,exemplary entity may be a financial service entity that provides,maintains, manages, or otherwise offers financial services. Suchfinancial service entity may be a bank, credit card issuer, or any othertype of financial service entity that generates, provides, manages,and/or maintains financial service accounts that entail providing one ormore apps to service one or more customers with authentication featuresenabling security measures such as challenge based authentication,multi-factor authentication, and the like. Financial service accountsmay include, for example, credit card accounts, bank accounts such aschecking and/or savings accounts, reward or loyalty program accounts,debit account, and/or any other type of financial service account knownto those skilled in the art.

FIG. 1 depicts an exemplary system 100 for improved challenge basedauthentications involving enhanced OTP messaging, in accordance with oneor more embodiments of the present disclosure. System 100 may include aserver 101 and a mobile device 160, which may communicate 103 over acommunication network 105. As illustrated herein, the mobile device 160may include any computing device or similar device through which a userof the mobile device 160 can access, via an app 107 executing on themobile device 160, the services and/or data provided at the server 101.As used herein, such an app 107 may include a web browser or other typeof app that permits a user to perform various actions with regard to theservices provided at the server 101.

In some embodiments, the business or merchant associated with the app107, typically a financial institution such as a credit card companythat has issued a debit card or a credit card to the user, may wish toallow the user accesses to the services provided via the app 107 uponauthentications triggered by a variety of conditions. For example, suchauthentication may be required after the user entering the correctcredentials (e.g., a pair of user name and password) configured inassociation with the app upon the user logging in the app, or after theuser logs into the app and during the course of the user attempting toperform certain activities (e.g., updating the profile settings ofpassword, phone number, email address, etc., conducting varioustransactions, such as purchasing transactions, account withdrawaltransactions, fund transfer transactions, of an amount exceeding athreshold) via the app 107. In various embodiments, the authenticationprocess may cause the server 101 to transmit the OTP information viaenhanced OTP messaging to the mobile device 160 for secure display andtransferal to the app 107. In some embodiments, the OTP may be segmentedby the server 101 into multiple parts for transmission to the mobiledevice 160 via distinct respective messaging channels (e.g., SMS, MMS,email, chat app). In some embodiments, the OTP may be anonymized theserver 101 into an unreadable format such that when received anddisplayed at the mobile device 160, the user cannot comprehend the realcontent of the OTP (e.g., a random N- digit code, a random sequence of Nimages or symbols or animations, a random N number of alphanumericcharacters, or a combination thereof). In some embodiments, as the usercannot read out or write down the real content of the OTP, the only wayto transfer the real content of the OTP from the receiving messaging appto the app 107 is via a restrictive transfer mechanism provided by themessaging app. Details of the enhanced OTP messaging and the restrictivetransfer are described with connection to FIGS. 2, and 3A-3C.

Still referring to FIG. 1 , server 101 may include at least oneprocessor 102, and a memory 104, such as random-access memory (RAM). Insome embodiments, server 101 may be operated by the entity issuing acredit card, a debit card, by the merchant, and/or by any transactionprocessing entity involved with authenticating users for access. In someembodiment, the memory 104 may be configured to store code, whenexecuted by processor 102, may cause the processor 102 to implement oneor more functionalities of the enhanced OTP messaging server 106, forcommunicating messages at various modalities with the mobile device 160.In some embodiments, the server 101 may be coupled with a third-partymessaging server to communicate in the form of messages with the mobiledevice 160.

In various embodiment, the enhanced OTP messaging server 106 mayimplement one or more aspects of various enhanced OTP messaging schemesherein, including those involving: (1) generating an OTP in response toa request pertaining to an authentication requirement, (2) segmenting anOTP into at least a first part and the second part, (3) anonymizing atlast part of the OTP into an unreadable format, (4) generating at leastpart of the OTP message to include a security token, (5) customizing thecontent and/or the format of the OTP messages, (6) transmitting thefirst part and the second part via distinct messaging app/messagingchannels to the requesting device, (7) causing the OTP only transferableto the authentication process via one or more graphical user interface(GUI) elements of a GUI of the messaging app, and/or (8) transmittingthe second part to the requesting device upon receiving the indicationthat the first part has been received and transferred to theauthentication process.

Mobile device 160, such as a smart phone or other portable or wirelessor wearable electronic device, may include mobile device circuitry 162.Mobile device circuitry 162 may include a mobile device processor 125,memory 120 such as RAM, computer-readable media, communication circuitryand interface 140, and/or any input and/or output device 121, such as atouchscreen display 135. The memory may store code that, when executedby the processor, may cause the processor to implement one or moreaspects of allowing a user to perform challenge based authenticationutilizing the enhanced OTP messaging schemes herein, including thoseinvolving: (1) sending an OTP request in response to the user operatesan app executing on the mobile device 160, (2) displaying the OTPmessage received at a messaging app, and/or (3) allowing the user toutilize one or more graphical user interface (GUI) elements of a GUI ofthe messaging app to transfer the OTP information to the app.

Mobile device may also display various graphical user interfaces that auser may utilize to perform challenge based authentications via enhancedOTP messaging features herein. Non-limiting examples are illustratedwith connection to FIGS. 3A-3C, below. Further, in some embodiments,mobile device 160 may be configured to operate in conjunction with othercomputing devices (e.g., a desktop or a laptop), at which the apppending authentication is executing. In this example, the mobile devicemay be configured to operate to provide at least one messagingapp/channel to implement the enhanced OTP messaging schemes herein.

Various embodiments associated with FIG. 1 and related disclosure hereinsolve a technical problem of providing challenge based authenticationswith enhanced security against frauds like voice phishing. Variousembodiments are implemented based on features and functionalityincluding enhancing OTP embedding messages as well as the transmissionand transfer thereof such that the OTP information received anddisplayed at the mobile device 160 no longer is subject to frauds oraccidents leading to the cases where an illegitimate user obtains theOTP and authenticates as a legitimate user to access the services/dataassociated with the legitimate user.

Various embodiments of the disclosure herein further solve anothertechnical problem of providing challenge based authentication withenhanced security against counterfeit OTP messages transmitted fromfraudulent parties. Various embodiments are implemented based onfeatures and functionality including enhancing OTP messages with asecurity token indicative of the authorization identity associated withthe OTP server. Such security token may be configured by the user inassociation with the app 107 and stored in a database accessible to theserver 101. A security token may also be dynamically generated andtransmitted to the user via different modalities for cross-verificationin real time, alleviating the user from memorizing the pre-configuredsecurity token associated with the app 107.

Further, various embodiments of the disclosure herein also solve anothertechnical problem of providing challenge based authentication withenhanced completion rate in terms of utilizing the OTP to complete therequired authentication. Various embodiments are implemented based onfeatures and functionality including enhancing OTP messages withcustomized content and format with which the user is more likely tointeract therewith. The content and/or format of OTP message may becustomized using various machine learning techniques such as an AI modelestablished based on the user's historical and habitual data, and agroup of users' historical and habitual data.

While only one server 101, network 105, mobile device 160, and app 107are shown, it will be understood that system 100 may include more thanone of any of these components. More generally, the components andarrangement of the components included in system 100 may vary. Thus,system 100 may include other components that perform or assist in theperformance of one or more processes consistent with the disclosedembodiments. For instance, the system may further include a computingdevice (not shown) which has the app 107 executing thereon, but notequipped with wireless communication capabilities to be able to receiveSMS messages. In this scenario, the server 101 may be configured todynamically detecting that the user operates the app 107 at a devicewithout the SMS messaging capabilities, and thereby causing the enhancedOTP messaging to be performed with connection with messaging appsoperative at modalities other than the SMS (e.g., email, chat channels).Nevertheless, the server 101 may also be configured to still perform theenhanced OTP messaging via the SMS app executing on the mobile device160, at the same time enabling the SMS app to activate a cross-devicerestrictive transfer (e.g., air drop to specific app only) from themobile device 160 to the app 107 running on the computing device, uponthe user's operation of such transfer. The following illustratesembodiments of the disclosure using examples of a mobile device that maybe configured to execute at least two messaging app to be able to atleast receive messages at the two respective messaging modalities, aswell as to execute the app 107.

FIG. 2 shows a diagram of an exemplary challenge based authenticationsystem involving enhanced OTP messaging, consistent with disclosedembodiments. In some embodiments, the challenge based authenticationsystem may include a server system 202 and a client system 204. As shownin this example, the server system 202 may include an anonymizing engine222, a split engine 224, an artificial intelligence (AI) engine 226, anda security token engine 228. The client system 204 may include an app212, a first messaging app 214, and a second messaging app 216.According to various aspects of the disclosure, the app 212 may be a webbrowser or any type of app that requires authentication of a userinteracting therewith. In some embodiments, the authentication is basedon the user entering into the app 212 information that matches up withthe supplemental information transmitted from the server system 202 tothe client system 204. In various embodiments, such supplementalinformation may be communicated independently from the app 212 viachannels such as messaging channels. In some embodiments, thesupplemental information may comprise an authentication factor which canbe utilized to authenticate the user. In one example, the authenticationfactor may include an OTP. In some embodiments, the app 212 mayimplement the app 107 of FIG. 1 .

In various implementations, the first messaging app and the secondmessaging app may be configured to receive the supplemental informationfrom the server system 202 at the client system 204 as distinctmodalities. For example, the first messaging app may be an SMS app;while the second messaging app may be an email app, or a chat app.Various embodiments herein may be configured such that the firstmessaging app and the second messaging app are enabled with arestrictive transfer user interface (UI) element to allow the user toprovide the OTP information to the app 212. The details of exemplaryrestrictive transfer UIs are illustrated with connection to FIGS. 3A-3C,below.

The server system 202 may generate the supplemental informationresponsive to receiving a request from the client system 204. In variousembodiments, the request may be generated upon the user operates the app212 to a stage when the above-described authentication requirement isinvoked. The generated supplemental information may be further fortifiedbased on the processing of at least one of the anonymizing engine 222,the split engine 224, the AI engine 226, and the security token engine228. In some embodiments, the server system 202 may also be configuredto generate the respective portions of the supplemental information,which are provided to at least one of the anonymizing engine 222, thesplit engine 224, the AI engine 226, and the security token engine 228for fortification, in a piecemeal fashion. In some embodiments, the AIengine 226 and the security token engine 228 may be configured tospecify features of the messages embedding the supplemental informationfor transmitting to the client system 204. For example, the AI engine226 and/or the security token engine 228 may be configured todynamically specify the content and/or the format of the messages withthe supplemental information embedded therein.

In various embodiments, the split engine may be configured to segmentinput supplemental information into a plurality of parts. In someembodiments, the split engine may be configured to divide thesupplemental information generated by the server system 202 into atleast two parts: a first part and a second part, for transmission to theclient system 204 separately via different messaging channels. In someembodiments, the first part of the supplemental information may betransmitted to the client system 204 in response to the request from theclient system 204; while the second part of the supplemental informationmay be transmitted to the second messaging app 216 in response to thefirst part being received by the messaging app 214 and transferred intothe app 212.

In various embodiments, the anonymizing engine 222 may be configured totransform input supplemental information into anonymized data. In someembodiments, the input information may include one or both of the firstpart of the supplemental information and the second part of thesupplemental information. Any suitable techniques may be applied torender the input supplemental information into an unreadable format.Non-limiting examples of anonymized data may include: a stringcomprising one or more of randomized letters, numbers, and symbols; animage; an icon; an animation; and text including text in a languageforeign to the user. In one example, the anonymized data may be entirelyobfuscated such that the user is presented with a message informing ofthe use of a restrictive transfer GUI of the messaging apps to transferthe supplemental information (or portions thereof) into the app 212. Inother words, the messaging apps may be configured not to display thesupplemental information at all in the messages received, only allowingthe transfer thereof to the app 212.

In various embodiments, the security token engine 228 may be configuredto include a security token in the message of the supplementalinformation. According to various aspects of the disclosure, thesecurity token may include one or more of: an image; a pass phrase; atone; a displaying color; a displaying motif; and a displaying floatingicon. In some embodiments, a security token may be pre-configured by theuser for the account associated with the app 212, and stored in adataset. In this case, a security token may be identified by thesecurity token engine 228 based on the request from the client system204. In some embodiments, the security token may be dynamicallygenerated and transmitted to the user via another communication channel.If the user is able to match the security token included with thesupplemental information with the security token sent in the othercommunication channel, then the messages comprising the supplementalinformation are deemed as being transmitted from an authentic serverinstead of a fraudulent party. In some embodiments, the security tokenincluded in the message is displayed to the user in association with theanother app. In some embodiments, a security token is included in one orboth of the message of the first part of the supplemental information,and the message of the second part of the supplemental information.

In various embodiments, the AI engine 226 may be configured to customizethe content and/or the format of the messages including the supplementalinformation. The AI engine 226 may include one or more modelsestablished, trained, and retrained by any suitable machine learningalgorithms, in conjunction with training datasets. In some embodiment,training datasets may include a number of training examples embodying apatterned occurrence in association with challenge basedauthentications. Each training example may include a number of (i.e.,one or more) observed features (e.g., the content of the OTP messages,channels of the OTP messages) related to a known outcome (e.g., whetherthe user clicks through to complete the authentication). With the one ormore models, the AI engine 226 may be configured to customize thecontent of the messages comprising the supplemental information based onone or more of: demographic data of the user; historical behavior dataof the user; demographic data of a group of users; and historicalbehavior data of the group of users. In one example, the AI engine 226may generate the OTP messages to include a favorite emoji of the user,cause the first part of the supplemental information to be transmittedto the mobile device of the user first, and the like.

In various embodiments, the AI engine 226 may be configured to furthercustomize the format of the messages comprising the supplementalinformation. In some embodiments, the AI engine 226 may customize suchas message for being displayed differently via one or more of: a previewbadge of GUI of the another app, a push notification the GUI of theanother app, a full-blown GUI of the another app, information of themobile device, and information of an operating system of the mobiledevice. For example, upon detecting the operating system of the user'smobile device is an Android system, the AI engine 226 may generate theOTP messages such that when displayed in a preview badge on a userinterface (UI) of the messaging app at the mobile device, the messagingapp is enabled with an operable GUI element (e.g., a “copy code”button), without displaying the anonymized supplemental information atthe UI. For another example, upon detecting the operating system of theuser's mobile device is an iOS system, the AI engine 226 may generatethe message such that, when displayed at the push notification on theGUI of the messaging app, the supplemental information is displayed inthe unreadable format and as an operable GUI element to allow the userto select to transfer to the app 212, without displaying separatelyanother GUI element such as a “copy code” button on the UI.

Further, it should be appreciated that one or more of the illustrativecomponents/modules/engines in FIG. 2 may include other components,sub-components, modules, sub-modules, and device commonly found in acommunication/computing system, which are not discussed above withreference to challenge based authentication system and not discussedherein for clarity of the description. Additionally, in someembodiments, one or more of the illustrative components/modules/enginescan form a portion of another component/module/engine and/or one or moreof the illustrative components/modules can be independent of oneanother.

FIGS. 3A-3C are schematic diagrams of certain illustrative aspects ofexemplary user interfaces for enabling a user to perform challenge basedauthentication via enhanced OTP messaging, consistent with exemplaryaspects of certain embodiments of the present disclosure. Referring toFIG. 3A, a simplified schematic diagram showing an exemplary messagingapp 302 displayed atop an app 320 is illustrated at the left hand side.Here, the app 320 has progressed to the stage where authentication isrequired before the user is able to further operate the app 320 toaccess its functionalities. As shown in this example, the app 320displays a text message informing the user that “For your security,verify this is you by entering the temporary 6-digit code we sent to(***) ***-3288” in a text panel 321. The app 320 further displays a textfield 322 for the user to enter the verification code when it isreceived.

As illustrated herein FIG. 3A, at this point of time, the user hasalready received the first part of the supplemental information (e.g.,OTP) at the first messaging app 302. In this example, the firstmessaging app is shown as an SMS app, which displays the received firstpart of the OTP in a banner display. As shown herein, the bannerdisplays that the message is sent from an entity 314 associated with“227896” and only partial content of the OTP message is displayed.Detecting that the message contains OTP information, the first messagingapp 302 is configured to present to the user a “COPY CODE” button 312.As such, the user does not need to expand on the GUI of the firstmessaging app 302 to access the first part of the OTP in order to copythe code into the app 320. Instead, the user can select the “COPY CODE”button 312, and subsequently pasts into the text field 322 of the app320 shown on the right hand side. In this example, upon receiving thetransferred first part of the OTP, the app 320 displays the content ofthe first part of the OTP as three dots 306 to safeguard the content.

Next, as illustrated on the left hand side of FIG. 3B, the user receivesthe second part of the OTP in the second messaging app. Here, the secondmessaging app is illustrated as an email app 332. As shown herein, theemail app 332 displays in the “From” field 334 that the email message issent from Capital One; in the “To” field 338 that the email message isdirected to the user at the email address of customer@gamil.com, and inthe subject field 336 that “Capital One: You authentication code.”Further, the email app 332 further displays the anonymized second part352 of the OTP as part of the content in body field 350. Similarly, theanonymized second part 352 of the OTP is rendered by the email app 332as an operable link. Upon the user's selection of the displayed secondpart, and a subsequent operation to paste into the text field 322 of theapp 320 shown at the right hand side of FIG. 3B, the real content of thesecond part of the OTP is transferred securely from the email app 332 tothe app 320, without the user or other parties being able to comprehendthe real content of the second part of the OTP. In some embodiment, inorder to prevent the user from entering the second part (or the firstpart) of the OTP displayed in the unreadable format into the text field322, the app 320 may be configured not accept the information keyed bythe user into the text field 322. For example, when the user attempts tokey the anonymized data “*@#” as the second part of the OTP into the app320, the app 320 may be configured not to accept input from inputdevices such as a keyboard, soft keyboard, or voice input. Instead,although not shown here, the app 320 may be configured to display analert window to notify the user that the OTP information can only betransferred thereinto via interacting with the operable informationitself, and/or via the GUI element that enables the transfer. As shownherein at the right hand side of FIG. 3B, at this point of time the textfield 322 is now populated with six dots 326, indicating that the app320 has received the complete OTP and is ready to authenticate the userbased on the received OTP.

FIG. 3C further illustrates two exemplary user interfaces of themessaging apps associated with the enhanced OTP messaging. As shown onthe left hand side of FIG. 3C, upon receiving an OTP message, themessaging app displays the OTP message in a push notification window360. Here, in this example, a “COPY CODE” button 362 is rendered anddisplayed at the push notification window 360, in which the entirecontent of the OTP message is not displayed. Also shown herein the righthand side of FIG. 3C, upon receiving an OTP message, the messaging appdisplays the OTP message in a full-blown window 380. Here, the OTPmessage 382 is displayed with a “COPY CODE” button 386 in the textconversation thread. Further, as the OTP message 382 is rendered incompleteness for display, the anonymized OTP information of “&&&” 384 isfurther rendered and displayed as an operable link. As such, the usermay choose to either select the “COPY CODE” button 386, or the operablelink embedded in the anonymized OTP information 384 to initiatetransferring the OTP information to the text field 322 of the app 320.

FIG. 4A is a flowchart illustrating one exemplary process 400 related toproviding challenge based authentication via enhanced OTP messaging,consistent with exemplary aspects of certain embodiments of the presentdisclosure. Referring to FIG. 4A, an illustrative process 400 related toproviding enhanced OTP messaging based authentication at a computingdevice may comprise: receiving a request from an application (app)executing on a computing device of a user, at 402; generating thesupplemental information based on the request, at 404; segmenting thesupplemental information into a first part of the supplementalinformation and a second part of the supplemental information, at 406;transmitting the first part of the supplemental information to thecomputing device of the user via a first communication channel toanother app executing on the computing device of the user, at 408;instructing the another app to allow the user to utilize one or moregraphical user interface (GUI) elements of a GUI of the another app totransfer the first part of the supplemental information to the app, at410; receiving an indication of the transferring, at 412; andtransmitting based on the indication of the transferring, the secondpart of the supplemental information to the computing device of the uservia a second communication channel so as to provide the supplementalinformation to the app, at 414. Further, such illustrative process 400may be carried out, in whole or in part, via or in conjunction with thecomputing device user interface described above with reference to FIGS.3A-3C.

According to the illustrative embodiment shown in FIG. 4A, process 400may include, at 402, a step of receiving a request from an application(app) executing on a computing device of a user. With regard to variousaspects of the disclosure, the request may be transmitted in response tothe user operating the app to a stage where supplemental information isrequired to further operate one or more functionalities of the app. Anillustration of a user interface of one such app is shown and discussedwith connection to the FIGS. 3A-3B. In some embodiments, the request forthe supplemental information is transmitted from the computing device atvarious stages during the user's interaction with the app. In oneexample, the request is received upon the user signs-in the app suchthat the user has to authenticate himself/herself using the supplementalinformation, in addition to providing the correct login credential atthe app. In another example, the request is received upon the useroperates the app to perform actions such as changing the password,changing the email associated with the app, making an in-app purchaseover a threshold amount, and so on, after the user has signed-into theapp.

The process 400 may include, at 404, a step of generating thesupplemental information based on the request; and at 406, a step ofsegmenting the supplemental information into a first part of thesupplemental information and a second part of the supplementalinformation. In some embodiments, the supplemental information may begenerated by the server 101 of FIG. 1 , or the server system 202 of FIG.2 , upon receiving the request from the user at the app. In someembodiments, the supplemental information may comprise an authenticationfactor, which can be used to authenticate the user operating the app. Insome embodiments, the authentication factor may include an OTP. Forexample, the OTP may be configured as a random N-digit code that expiresafter a pre-configured period of time after transmission or generation.In various embodiment, N can be configured as any number suitable forthe user's operation at the app, level of security measures configuredat the server for the types of access the user attempts at the app,contexts relating to the user's operations at the app, and the like. Forexample, N is between 4 to 8. For example, N is 4. For example, N is 5.For example, N is 6. For example, N is 7. For example, N is 8. In otherexamples, the OTP may also be configured as a pseudorandom N-digit code.In yet some other example, the OTP may be configured as a randomsequence of N images/symbols/animations/alphanumeric characters, or acombination thereof. Any suitable techniques can be utilized to generatesuch random/pseudorandom sequence of N data items. By way ofnon-limiting examples, random numbers may be generated by the use of:Monte Carlo methods, MIXMAX generator, Multiply-with-carry methods,Xorshift methods, Advanced Randomization System, and the like. Also, byway of non-limiting examples, pseudorandom numbers may be generated bythe use of: Lehmer generator, Linear congruential generator,Wichmann-Hill generator, Park-Miller generator, Multiply-with-carrymethod, Permuted Congruential Generator, and the like.

In some embodiments, the first part of the supplemental information maybe anonymized into unreadable format before being communicated to theapp. According to various aspects of the disclosure, the supplementalinformation may be anonymized into data comprising, without limitation,one or more of: a string comprising, without limitation, one or more ofrandomized letters, numbers, and/or symbols; a visual content (e.g.,image, video, visual animation, etc.); visual-audio content (e.g.,video, voiced visual animation, etc.); audio content; and/or text in alanguage foreign to the user. As a result, the anonymized supplementalinformation, when received and displayed at a messaging app executing onthe computing device, the supplemental information no longer is notreadable for the user, thereby restricting the transfer of the realcontent of supplemental information to the app to the above-describedGUI elements of the messaging app. In other words, the user or otherparties no longer is able to read out or write down the supplementalinformation for being keyed into the app.

In some embodiments, the first part of the supplemental information maybe anonymized such that the entire content of the supplementalinformation is, without limitation, in a form of animation (e.g., visualanimation with or without voice, audio-only recording) that is notpresented (e.g., displayed, voiced, or both) at the same time. In oneexample, the first part (e.g., a string of 3 digits/letters/symbols) ofthe supplemental information may be presented in the form of a visualpresentation where the first digit/letter/symbol may be displayed for afirst pre-configured duration of time (e.g., 1 second), the seconddigit/letter/symbol may be next displayed for a second pre-configuredduration of time (e.g., 1 second), and lastly the thirddigit/letter/symbol may be displayed for a third pre-configured durationof time (e.g., 1 second).

In some embodiments, the first part of the supplemental information maybe anonymized such that the entire content of the supplementalinformation may be embedded in camouflaging content items for displayingat the same time. In one example, an animation may be configured todisplay “123−23+7” to indicate to the user that the supplementalinformation is a string of six digits of “123237” despite thecamouflaging content items of “−” and “+” displayed simultaneously. Inanother example, an animation may be configured to display “123” typedout, followed with two deletions and “07” typed out to indicate to theuser that the supplemental information is also a string of six digits of“123237”. In yet another example, an animation may be configured todisplay “123 twice” or “enter 123 twice” to indicate to the user thatthe supplemental information is a string of six digits of “123123”. Instill yet another example, an animation may be configured to display thefirst part of the supplemental information (e.g., half of the N digitsof an OTP, one third of the N digits of an OTP) for a predetermined timeperiod (e.g., 1 second), along with a formula or an instruction of thesteps indicating to the user how to compose or otherwise interpret thefull content of the supplemental information based on the animationdisplayed thereto. In those scenarios, the user may choose to manuallyenter the interpreted supplemental information into the app.Alternatively, the messaging tool may nevertheless be configured toextract the supplemental information for transferring to the app. Insome embodiments, the anonymized information may be transferred to theapp both in the conventional manner (e.g., the user enters theinformation) and the restricted manner (e.g., user operates the GUIelement to cause the messaging tool to transfer to the app).

The process 400 may include, at 408, a step of transmitting the firstpart of the supplemental information to the computing device of the uservia a first communication channel to another app executing on thecomputing device of the user. In various embodiments, the first part ofthe supplemental information and the second part of the supplementalinformation may be embedded in the respective messages for communicationto the respective messaging apps executing on the user's computingdevice. The another app may be any app configured to receive the firstpart of the supplemental information. Here, as illustrated in connectionwith FIGS. 3A-3C, the another app may be an SMS app or an email app. Inother examples, the another app may be a chat app, MMS app, or the like.Depending on the features of the another app, such a message mayidentify various information such as the identity of the sender, theidentity of a recipient, a subject line, a timestamp, as well as amessage body including the supplemental information (e.g., the firstpart and/or the second part). Examples of the messages are shown anddiscussed in connection with FIGS. 3A-3C, above.

In some embodiments, the messages may be customized for being displayeddifferently at the another app. Here, for example, the messages may becustomized for being displayed differently at one or more of: a previewbadge GUI of the another app, a push notification GUI of the anotherapp, a full-blown GUI of the another app, information of the computingdevice, and information of an operating system of the computing device.Information of the computing device may include data pertaining to thehardware, software, and/or firmware of the computing device, datapertaining to the manufacturer, manufacturing date, operator, and so on.Information of an operating system of the computing device may includedata pertaining to the versions, release dates, updates, patches, and soon. Illustrations of exemplary preview badge (banner) GUI, a pushnotification GUI, as well as a full-blown GUI of the another app areshown and discussed with connection to FIGS. 3A-3C, above.

In some embodiments, the messages may also be generated with customizedcontent for being displayed at the another app. The message content maybe customized based on various factors. For example, the message contentmay be customized according to data of the user, data of a group ofusers, as well as the above-discussed information of the computingdevice, and information of the operating system of the computing device.For instance, user data may comprise demographic data of the user andhistorical behavior data of the user. Data of a group of users maycomprise demographic data of a group of users; and historical behaviordata of the group of users. In various embodiments, with insight andintelligence respecting the user, similar users, user's computingdevice's capabilities and functionalities, both the format and contentof the message may be customized to better appeal to the user, therebycontributing to a higher completion rate with regard to challenge basedauthentication involving the supplemental information.

The process 400 may include, at 410, a step of instructing the anotherapp to allow the user to utilize one or more graphical user interface(GUI) elements of a GUI of the another app to transfer the first part ofthe supplemental information to the app; at 412, a step of receiving anindication of the transferring; and at 414, a step of transmitting,based on the indication of the transferring, the second part of thesupplemental information to the computing device of the user via asecond communication channel so as to provide the supplementalinformation to the app. Various embodiments herein may be configuredsuch that the transferring of the supplemental information comprisespopulating the one or more GUI elements of the GUI of the app with thesupplemental information to enable the user to operate the one or morefunctionalities of the app. In some embodiments, the supplementalinformation may be completely transferred to the app upon both the firstpart and the second part of the supplemental information have beenprovided to the app via user's operation of the one or more GUIs of theanother app (and other apps).

In some embodiments, process 400 may further include steps ofidentifying a security token associated with the user from a datasetconfigured for accounts of users associated with the app, and generatingthe respective messages based on the security token. According to someaspects of the disclosure, the security token may specify by the user ata prior time, and displayed to the user in association with the anotherapp. In implementations, the security token may comprise one or more of:an image, a passphrase, a tone, a displaying color, a displaying motif,and a displaying floating icon.

FIG. 4B is a flowchart illustrating one exemplary process 450 related toproviding challenge based authentication via enhanced OTP messaging,consistent with exemplary aspects of certain embodiments of the presentdisclosure. Referring to FIG. 4B, an illustrative process 450 related toproviding enhanced OTP messaging based authentication at a computingdevice may comprise: receiving a request from an application (app)executing on a computing device of a user to a server, at 452;generating the supplemental information based on the request, at 454;anonymizing a portion of the supplemental information into unreadableformat, at 456; transmitting the unreadable portion of the supplementalinformation in a message to a messaging app executing on the computingdevice, at 458; detecting that the user uses one or more graphical userinterface (GUI) elements of a GUI of the messaging app to transfer theunreadable portion of the supplemental information to the app, at 460;and causing, in response to the detecting, to provide a remaining partof the supplemental information to the app, at 462. Further, suchillustrative process 450 may be carried out, in whole or in part, via orin conjunction with the computing device user interface described abovewith reference to FIGS. 3A-3C.

According to the illustrative embodiment shown in FIG. 4A, process 400may include, at 402, a step of receiving a request from an application(app) executing on a computing device of a user to a server. With regardto various aspects of the disclosure, the request may be transmitted inresponse to the user operating the app to a stage where supplementalinformation is required to further operate one or more functionalitiesof the app.

In some embodiments, process 400 may further include a step ofgenerating the content of the message using a machine learning model. Inimplementations, the machine learning model may be trained usinghistorical completion rates and user demographic data associated withhistorical message content, historical message formats, and historicalmessage channels. In some embodiments, a training dataset may begenerated by collecting various features associated with OTP messages inrelation to the OTP messages' respective historical completion rates. Inaddition to the above-described demographic data, message content,message formats, and message channels, features associated with OTPmessage may further include data items including, but not limited to,contextual information relating to the OTP messages (e.g., transmittedat what time of day, date, etc.), contextual information relating to theuser's operation with regard to the OTP messages (e.g., received at whattime of day, date, accessed at what time of day, date, at what location,etc.), analytics data for the user (e.g., analytical data on user'sactivities and behaviors, e.g., whether the user has recently opened theapp, the frequency, time duration of the user's log-ins at the app, thetypes of actions the user performs with the app, etc.), and informationabout the device used last time to receive an OTP message (or accessingthe app, etc.).

In some embodiments, trained with the knowledge correlating the featuresrelating to historical OTP messages with the completion rates, themachine learning model learns which combinations of the features workbest in terms of incurring higher completion rates. For example, themachine model may be trained to learn that OTP messages reach youngerpopulations more successful with certain channels, at certain times,with certain types of devices, or any combinations of the OTP messagefeatures observed. For another example, the machine learning model maybe trained to learn that images in an MMS contribute to a better chanceof higher completion rates late at night (e.g., the MMS transmitted lateat night or the user accessing the MMS late at night). For yet anotherexample, the machine learning model may be trained to learn about theuser's behaviors (e.g., habits/schedule, etc.) based, at least in part,without limitation, on one or more user's interaction patterns with acomputing device(s) (e.g., smartphone, etc.). In some embodiments, basedon the learned user's behavior(s), the trained machine learning modelmay cause to transmit the OTP message to a computing device of the userwithout delay or introduce a time delay in transmitting the OTP message.Such a time delay may be configured, statically or dynamically, as anyduration of time suitable for the user, contexts of the user, and thelike. In one example, a time delay is configured as a number ofmilliseconds. Given the time delay suggested by the machine learningmodel, OTP messages may yield a better result in terms of completionrates as this would give the user time to context switch, or catch theuser at a more appropriate time, etc. In some instances, messaging timedelays may be learned and customized on an individual basis per user, orbased on other features relating to OTP messaging (e.g., features of theuser device, etc.).

In various embodiments, the machine learning model may take featuresrelating to OTP messages as input, and output a suggested messageformat(s), and/or suggested message content to use for a new OTPmessage. In some embodiments, the suggested message format may begenerated in an ordered list of message formats, with respective weightsfor their expected effectiveness attached thereto. In this scenario, A/Btests of different options may also be performed to gain intelligencewith regard to the effectiveness of OTP message features, rather thanrelying on a single result from the machine learning model.

In some embodiments, the machine learning model may be trained withtraining datasets of data collected based on multiple users' historicalinteractions with regard to OTP messages. In other embodiments, themachine learning model may be trained based on per-user optimization.For example, users may be segmented or clustered based on one or morecharacteristics (e.g., demographics, psychographics, socialmedia-related characteristics, etc.) such that information about thebest segment for each user can be stored and utilized to recommendmessage format(s)/content for future OTP messaging for communicationwith the user (e.g., using unsupervised learning).

According to various embodiments of the disclosure, with insight andintelligence provided by the machine learning model (and othertechniques), various aspects of the message including both the formatand content may be customized to better appeal to the user, therebycontributing to a higher completion rate with regard to challenge basedauthentication involving the supplemental information.

FIG. 5 depicts a block diagram of an exemplary computer-basedsystem/platform in accordance with one or more embodiments of thepresent disclosure. However, not all of these components may be requiredto practice one or more embodiments, and variations in the arrangementand type of the components may be made without departing from the spiritor scope of various embodiments of the present disclosure. In someembodiments, the exemplary inventive computing devices and/or theexemplary inventive computing components of the exemplary computer-basedsystem/platform may be configured to manage a large number of instancesof software applications, users, and/or concurrent transactions, asdetailed herein. In some embodiments, the exemplary computer-basedsystem/platform may be based on a scalable computer and/or networkarchitecture that incorporates varies strategies for assessing the data,caching, searching, and/or database connection pooling. An example ofthe scalable architecture is an architecture that is capable ofoperating multiple servers.

In some embodiments, referring to FIG. 5 , members 702-704 (e.g., POSdevices or clients) of the exemplary computer-based system/platform mayinclude virtually any computing device capable of receiving and sendinga message over a network (e.g., cloud network), such as network 705, toand from another computing device, such as servers 706 and 707, eachother, and the like. In some embodiments, the member devices 702-704 maybe personal computers, multiprocessor systems, microprocessor-based orprogrammable consumer electronics, network PCs, and the like. In someembodiments, one or more member devices within member devices 702-704may include computing devices that typically connect using wirelesscommunications media such as cell phones, smart phones, pagers, walkietalkies, radio frequency (RF) devices, infrared (IR) devices, CBs,integrated devices combining one or more of the preceding devices, orvirtually any mobile computing device, and the like. In someembodiments, one or more member devices within member devices 702-704may be devices that are capable of connecting using a wired or wirelesscommunication medium such as a PDA, POCKET PC, wearable computer, alaptop, tablet, desktop computer, a netbook, a video game device, apager, a smart phone, an ultra-mobile personal computer (UMPC), and/orany other device that is equipped to communicate over a wired and/orwireless communication medium (e.g., NFC, RFID, NBIOT, 3G, 4G, 5G, GSM,GPRS, WiFi, WiMax, CDMA, satellite, ZigBee, etc.). In some embodiments,one or more member devices within member devices 702-704 may include mayrun one or more applications, such as Internet browsers, mobileapplications, voice calls, video games, videoconferencing, and email,among others. In some embodiments, one or more member devices withinmember devices 702-704 may be configured to receive and to send webpages, and the like. In some embodiments, an exemplary specificallyprogrammed browser application of the present disclosure may beconfigured to receive and display graphics, text, multimedia, and thelike, employing virtually any web based language, including, but notlimited to Standard Generalized Markup Language (SMGL), such asHyperText Markup Language (HTML), a wireless application protocol (WAP),a Handheld Device Markup Language (HDML), such as Wireless MarkupLanguage (WML), WMLScript, XML, JavaScript, and the like. In someembodiments, a member device within member devices 702-704 may bespecifically programmed by either Java, .Net, QT, C, C++ and/or othersuitable programming language. In some embodiments, one or more memberdevices within member devices 702-704 may be specifically programmedinclude or execute an application to perform a variety of possibletasks, such as, without limitation, messaging functionality, browsing,searching, playing, streaming or displaying various forms of content,including locally stored or uploaded messages, images and/or video,and/or games.

In some embodiments, the exemplary network 705 may provide networkaccess, data transport and/or other services to any computing devicecoupled to it. In some embodiments, the exemplary network 705 mayinclude and implement at least one specialized network architecture thatmay be based at least in part on one or more standards set by, forexample, without limitation, GlobalSystem for Mobile communication (GSM)Association, the Internet Engineering Task Force (IETF), and theWorldwide Interoperability for Microwave Access (WiMAX) forum. In someembodiments, the exemplary network 705 may implement one or more of aGSM architecture, a General Packet Radio Service (GPRS) architecture, aUniversal Mobile Telecommunications System (UMTS) architecture, and anevolution of UMTS referred to as Long Term Evolution (LTE). In someembodiments, the exemplary network 705 may include and implement, as analternative or in conjunction with one or more of the above, a WiMAXarchitecture defined by the WiMAX forum. In some embodiments and,optionally, in combination of any embodiment described above or below,the exemplary network 705 may also include, for instance, at least oneof a local area network (LAN), a wide area network (WAN), the Internet,a virtual LAN (VLAN), an enterprise LAN, a layer 3 virtual privatenetwork (VPN), an enterprise IP network, or any combination thereof. Insome embodiments and, optionally, in combination of any embodimentdescribed above or below, at least one computer network communicationover the exemplary network 705 may be transmitted based at least in parton one of more communication modes such as but not limited to: NFC,RFID, Narrow Band Internet of Things (NBIOT), ZigBee, 3G, 4G, 5G, GSM,GPRS, WiFi, WiMax, CDMA, satellite and any combination thereof. In someembodiments, the exemplary network 705 may also include mass storage,such as network attached storage (NAS), a storage area network (SAN), acontent delivery network (CDN) or other forms of computer- ormachine-readable media.

In some embodiments, the exemplary server 706 or the exemplary server707 may be a web server (or a series of servers) running a networkoperating system, examples of which may include but are not limited toMicrosoft Windows Server, Novell NetWare, or Linux. In some embodiments,the exemplary server 706 or the exemplary server 707 may be used forand/or provide cloud and/or network computing. Although not shown inFIG. 5 , in some embodiments, the exemplary server 706 or the exemplaryserver 707 may have connections to external systems like email, SMSmessaging, text messaging, ad content providers, etc. Any of thefeatures of the exemplary server 706 may be also implemented in theexemplary server 707 and vice versa.

In some embodiments, one or more of the exemplary servers 706 and 707may be specifically programmed to perform, in non-limiting example, asauthentication servers, search servers, email servers, social networkingservices servers, SMS servers, IM servers, MMS servers, exchangeservers, photo-sharing services servers, advertisement providingservers, financial/banking-related services servers, travel servicesservers, or any similarly suitable service-base servers for users of themember computing devices 701-704.

In some embodiments and, optionally, in combination of any embodimentdescribed above or below, for example, one or more exemplary computingmember devices 702-704, the exemplary server 706, and/or the exemplaryserver 707 may include a specifically programmed software module thatmay be configured to send, process, and receive information using ascripting language, a remote procedure call, an email, a tweet, ShortMessage Service (SMS), Multimedia Message Service (MMS), instantmessaging (IM), internet relay chat (IRC), mIRC, Jabber, an applicationprogramming interface, Simple Object Access Protocol (SOAP) methods,Common Object Request Broker Architecture (CORBA), HTTP (HypertextTransfer Protocol), REST (Representational State Transfer), or anycombination thereof.

FIG. 6 depicts a block diagram of another exemplary computer-basedsystem/platform 800 in accordance with one or more embodiments of thepresent disclosure. However, not all of these components may be requiredto practice one or more embodiments, and variations in the arrangementand type of the components may be made without departing from the spiritor scope of various embodiments of the present disclosure. In someembodiments, the member computing devices (e.g., POS devices) 802 a, 802b thru 802 n shown each at least includes computer-readable media, suchas a random-access memory (RAM) 808 coupled to a processor 810 and/ormemory 808. In some embodiments, the processor 810 may executecomputer-executable program instructions stored in memory 808. In someembodiments, the processor 810 may include a microprocessor, an ASIC,and/or a state machine. In some embodiments, the processor 810 mayinclude, or may be in communication with, media, for examplecomputer-readable media, which stores instructions that, when executedby the processor 810, may cause the processor 810 to perform one or moresteps described herein. In some embodiments, examples ofcomputer-readable media may include, but are not limited to, anelectronic, optical, magnetic, or other storage or transmission devicecapable of providing a processor, such as the processor 810 of client802 a, with computer-readable instructions. In some embodiments, otherexamples of suitable media may include, but are not limited to, a floppydisk, CD-ROM, DVD, magnetic disk, memory chip, ROM, RAM, an ASIC, aconfigured processor, all optical media, all magnetic tape or othermagnetic media, or any other media from which a computer processor canread instructions. Also, various other forms of computer-readable mediamay transmit or carry instructions to a computer, including a router,private or public network, or other transmission device or channel, bothwired and wireless. In some embodiments, the instructions may comprisecode from any computer-programming language, including, for example, C,C++, Visual Basic, Java, Python, Perl, JavaScript, and etc.

In some embodiments, member computing devices 802 a through 802 n mayalso comprise a number of external or internal devices such as a mouse,a CD-ROM, DVD, a physical or virtual keyboard, a display, a speaker, orother input or output devices. In some embodiments, examples of membercomputing devices 802 a through 802 n (e.g., clients) may be any type ofprocessor-based platforms that are connected to a network 806 such as,without limitation, personal computers, digital assistants, personaldigital assistants, smart phones, pagers, digital tablets, laptopcomputers, Internet appliances, and other processor-based devices. Insome embodiments, member computing devices 802 a through 802 n may bespecifically programmed with one or more application programs inaccordance with one or more principles/methodologies detailed herein. Insome embodiments, member computing devices 802 a through 802 n mayoperate on any operating system capable of supporting a browser orbrowser-enabled application, such as Microsoft™, Windows™, and/or Linux.In some embodiments, member computing devices 802 a through 802 n shownmay include, for example, personal computers executing a browserapplication program such as Microsoft Corporation's Internet Explorer™,Apple Computer, Inc.'s Safari™, Mozilla Firefox, and/or Opera. In someembodiments, through the member computing client devices 802 a through802 n, users, 812 a through 802 n, may communicate over the exemplarynetwork 806 with each other and/or with other systems and/or devicescoupled to the network 806.

As shown in FIG. 6 , exemplary server devices 804 and 813 may be alsocoupled to the network 806. In some embodiments, one or more membercomputing devices 802 a through 802 n may be mobile clients. In someembodiments, server devices 804 and 813 shown each at least includesrespective computer-readable media, such as a random-access memory (RAM)coupled to a respective processor 805, 814 and/or respective memory 817,816. In some embodiments, the processor 805, 814 may executecomputer-executable program instructions stored in memory 817, 816,respectively. In some embodiments, the processor 805, 814 may include amicroprocessor, an ASIC, and/or a state machine. In some embodiments,the processor 805, 814 may include, or may be in communication with,media, for example computer-readable media, which stores instructionsthat, when executed by the processor 805, 814, may cause the processor805, 814 to perform one or more steps described herein. In someembodiments, examples of computer-readable media may include, but arenot limited to, an electronic, optical, magnetic, or other storage ortransmission device capable of providing a processor, such as therespective processor 805, 814 of server devices 804 and 813, withcomputer-readable instructions. In some embodiments, other examples ofsuitable media may include, but are not limited to, a floppy disk,CD-ROM, DVD, magnetic disk, memory chip, ROM, RAM, an ASIC, a configuredprocessor, all optical media, all magnetic tape or other magnetic media,or any other media from which a computer processor can readinstructions. Also, various other forms of computer-readable media maytransmit or carry instructions to a computer, including a router,private or public network, or other transmission device or channel, bothwired and wireless. In some embodiments, the instructions may comprisecode from any computer-programming language, including, for example, C,C++, Visual Basic, Java, Python, Perl, JavaScript, and etc.

In some embodiments, at least one database of exemplary databases 807and 815 may be any type of database, including a database managed by adatabase management system (DBMS). In some embodiments, an exemplaryDBMS-managed database may be specifically programmed as an engine thatcontrols organization, storage, management, and/or retrieval of data inthe respective database. In some embodiments, the exemplary DBMS-manageddatabase may be specifically programmed to provide the ability to query,backup and replicate, enforce rules, provide security, compute, performchange and access logging, and/or automate optimization. In someembodiments, the exemplary DBMS-managed database may be chosen fromOracle database, IBM DB2, Adaptive Server Enterprise, FileMaker,Microsoft Access, Microsoft SQL Server, MySQL, PostgreSQL, and a NoSQLimplementation. In some embodiments, the exemplary DBMS-managed databasemay be specifically programmed to define each respective schema of eachdatabase in the exemplary DBMS, according to a particular database modelof the present disclosure which may include a hierarchical model,network model, relational model, object model, or some other suitableorganization that may result in one or more applicable data structuresthat may include fields, records, files, and/or objects. In someembodiments, the exemplary DBMS-managed database may be specificallyprogrammed to include metadata about the data that is stored.

As also shown in FIGS. 7 and 8 , some embodiments of the disclosedtechnology may also include and/or involve one or more cloud components825, which are shown grouped together in the drawing for sake ofillustration, though may be distributed in various ways as known in theart. Cloud components 825 may include one or more cloud services such assoftware applications (e.g., queue, etc.), one or more cloud platforms(e.g., a Web front-end, etc.), cloud infrastructure (e.g., virtualmachines, etc.), and/or cloud storage (e.g., cloud databases, etc.).

According to some embodiments shown by way of one example in FIG. 8 ,the exemplary inventive computer-based systems/platforms, the exemplaryinventive computer-based devices, components and media, and/or theexemplary inventive computer-implemented methods of the presentdisclosure may be specifically configured to operate in or with cloudcomputing/architecture such as, but not limiting to: infrastructure aservice (IaaS) 1010, platform as a service (PaaS) 1008, and/or softwareas a service (SaaS) 1006. FIGS. 7 and 8 illustrate schematics ofexemplary implementations of the cloud computing/architecture(s) inwhich the exemplary inventive computer-based systems/platforms, theexemplary inventive computer-implemented methods, and/or the exemplaryinventive computer-based devices, components and/or media of the presentdisclosure may be specifically configured to operate. In someembodiments, such cloud architecture 1006, 1008, 1010 may be utilized inconnection with the Web browser and browser extension aspects, shown at1004, to achieve the innovations herein.

As used in the description and in any claims, the term “based on” is notexclusive and allows for being based on additional factors notdescribed, unless the context clearly dictates otherwise. In addition,throughout the specification, the meaning of “a,” “an,” and “the”include plural references. The meaning of “in” includes “in” and “on.”

It is understood that at least one aspect/functionality of variousembodiments described herein can be performed in real-time and/ordynamically. As used herein, the term “real-time” is directed to anevent/action that can occur instantaneously or almost instantaneously intime when another event/action has occurred. For example, the “real-timeprocessing,” “real-time computation,” and “real-time execution” allpertain to the performance of a computation during the actual time thatthe related physical process (e.g., a user interacting with anapplication on a mobile device) occurs, in order that results of thecomputation can be used in guiding the physical process.

As used herein, the term “dynamically” and term “automatically,” andtheir logical and/or linguistic relatives and/or derivatives, mean thatcertain events and/or actions can be triggered and/or occur without anyhuman intervention. In some embodiments, events and/or actions inaccordance with the present disclosure can be in real-time and/or basedon a predetermined periodicity of at least one of: nanosecond, severalnanoseconds, millisecond, several milliseconds, second, several seconds,minute, several minutes, hourly, several hours, daily, several days,weekly, monthly, etc.

As used herein, the term “runtime” corresponds to any behavior that isdynamically determined during an execution of a software application orat least a portion of software application.

In some embodiments, exemplary inventive, specially programmed computingsystems/platforms with associated devices are configured to operate inthe distributed network environment, communicating with one another overone or more suitable data communication networks (e.g., the Internet,satellite, etc.) and utilizing one or more suitable data communicationprotocols/modes such as, without limitation, IPX/SPX, X.25, AX.25,AppleTalk™, TCP/IP (e.g., HTTP), Bluetooth™, near-field wirelesscommunication (NFC), RFID, Narrow Band Internet of Things (NBIOT), 3G,4G, 5G, GSM, GPRS, WiFi, WiMax, CDMA, satellite, ZigBee, and othersuitable communication modes. Various embodiments herein may includeinteractive posters that involve wireless, e.g., Bluetooth™ and/or NFC,communication aspects, as set forth in more detail further below. Insome embodiments, the NFC can represent a short-range wirelesscommunications technology in which NFC-enabled devices are “swiped,”“bumped,” “tap” or otherwise moved in close proximity to communicate. Insome embodiments, the NFC could include a set of short-range wirelesstechnologies, typically requiring a distance of 10 cm or less. In someembodiments, the NFC may operate at 13.56 MHz on ISO/IEC 18000-3 airinterface and at rates ranging from 106 kbit/s to 424 kbit/s. In someembodiments, the NFC can involve an initiator and a target; theinitiator actively generates an RF field that can power a passivetarget. In some embodiment, this can enable NFC targets to take verysimple form factors such as tags, stickers, key fobs, or cards that donot require batteries. In some embodiments, the NFL's peer-to-peercommunication can be conducted when a plurality of NFC-enable devices(e.g., smartphones) are within close proximity of each other.

The material disclosed herein may be implemented in software or firmwareor a combination of them or as instructions stored on a machine-readablemedium, which may be read and executed by one or more processors. Amachine-readable medium may include any medium and/or mechanism forstoring or transmitting information in a form readable by a machine(e.g., a computing device). For example, a machine-readable medium mayinclude read only memory (ROM); random access memory (RAM); magneticdisk storage media; optical storage media; flash memory devices;electrical, optical, acoustical or other forms of propagated signals(e.g., carrier waves, infrared signals, digital signals, etc.), andothers.

As used herein, the terms “computer engine” and “engine” identify atleast one software component and/or a combination of at least onesoftware component and at least one hardware component which aredesigned/programmed/configured to manage/control other software and/orhardware components (such as the libraries, software development kits(SDKs), objects, etc.).

Examples of hardware elements may include processors, microprocessors,circuits, circuit elements (e.g., transistors, resistors, capacitors,inductors, and so forth), integrated circuits, application specificintegrated circuits (ASIC), programmable logic devices (PLD), digitalsignal processors (DSP), field programmable gate array (FPGA), logicgates, registers, semiconductor device, chips, microchips, chip sets,and so forth. In some embodiments, the one or more processors may beimplemented as a Complex Instruction Set Computer (CISC) or ReducedInstruction Set Computer (RISC) processors; x86 instruction setcompatible processors, multi-core, or any other microprocessor orcentral processing unit (CPU). In various implementations, the one ormore processors may be dual-core processor(s), dual-core mobileprocessor(s), and so forth.

Examples of software may include software components, programs,applications, computer programs, application programs, system programs,machine programs, operating system software, middleware, firmware,software modules, routines, subroutines, functions, methods, procedures,software interfaces, application program interfaces (API), instructionsets, computing code, computer code, code segments, computer codesegments, words, values, symbols, or any combination thereof.Determining whether an embodiment is implemented using hardware elementsand/or software elements may vary in accordance with any number offactors, such as desired computational rate, power levels, heattolerances, processing cycle budget, input data rates, output datarates, memory resources, data bus speeds and other design or performanceconstraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that make the logic or processor. Of note, various embodimentsdescribed herein may, of course, be implemented using any appropriatehardware and/or computing software languages (e.g., C++, Objective-C,Swift, Java, JavaScript, Python, Perl, QT, etc.).

In some embodiments, one or more of exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay include or be incorporated, partially or entirely into at least onepersonal computer (PC), laptop computer, ultra-laptop computer, tablet,touch pad, portable computer, handheld computer, palmtop computer,personal digital assistant (PDA), cellular telephone, combinationcellular telephone/PDA, television, smart device (e.g., smart phone,smart tablet or smart television), mobile internet device (MID),messaging device, data communication device, and so forth.

As used herein, term “server” should be understood to refer to a servicepoint which provides processing, database, and communication facilities.By way of example, and not limitation, the term “server” can refer to asingle, physical processor with associated communications and datastorage and database facilities, or it can refer to a networked orclustered complex of processors and associated network and storagedevices, as well as operating software and one or more database systemsand application software that support the services provided by theserver. Cloud components (e.g., FIG. 7-8 ) and cloud servers areexamples.

In some embodiments, as detailed herein, one or more of exemplaryinventive computer-based systems/platforms, exemplary inventivecomputer-based devices, and/or exemplary inventive computer-basedcomponents of the present disclosure may obtain, manipulate, transfer,store, transform, generate, and/or output any digital object and/or dataunit (e.g., from inside and/or outside of a particular application) thatcan be in any suitable form such as, without limitation, a file, acontact, a task, an email, a tweet, a map, an entire application (e.g.,a calculator), etc. In some embodiments, as detailed herein, one or moreof exemplary inventive computer-based systems/platforms, exemplaryinventive computer-based devices, and/or exemplary inventivecomputer-based components of the present disclosure may be implementedacross one or more of various computer platforms such as, but notlimited to: (1) AmigaOS, AmigaOS 4; (2) FreeBSD, NetBSD, OpenBSD; (3)Linux; (4) Microsoft Windows; (5) OpenVMS; (6) OS X (Mac OS); (7) OS/2;(8) Solaris; (9) Tru64 UNIX; (10) VM; (11) Android; (12) Bada; (13)BlackBerry OS; (14) Firefox OS; (15) Ios; (16) Embedded Linux; (17) PalmOS; (18) Symbian; (19) Tizen; (20) WebOS; (21) Windows Mobile; (22)Windows Phone; (23) Adobe AIR; (24) Adobe Flash; (25) Adobe Shockwave;(26) Binary Runtime Environment for Wireless (BREW); (27) Cocoa (API);(28) Cocoa Touch; (29) Java Platforms; (30) JavaFX; (31) JavaFX Mobile;(32) Microsoft XNA; (33) Mono; (34) Mozilla Prism, XUL and XULRunner;(35) .NET Framework; (36) Silverlight; (37) Open Web Platform; (38)Oracle Database; (39) Qt; (40) SAP NetWeaver; (41) Smartface; (42) Vexi;and/OR (43) Windows Runtime.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to utilize hardwired circuitry that may be used inplace of or in combination with software instructions to implementfeatures consistent with principles of the disclosure. Thus,implementations consistent with principles of the disclosure are notlimited to any specific combination of hardware circuitry and software.For example, various embodiments may be embodied in many different waysas a software component such as, without limitation, a stand-alonesoftware package, a combination of software packages, or it may be asoftware package incorporated as a “tool” in a larger software product.

For example, exemplary software specifically programmed in accordancewith one or more principles of the present disclosure may bedownloadable from a network, for example, a website, as a stand-aloneproduct or as an add-in package for installation in an existing softwareapplication. For example, exemplary software specifically programmed inaccordance with one or more principles of the present disclosure mayalso be available as a client-server software application, or as aweb-enabled software application. For example, exemplary softwarespecifically programmed in accordance with one or more principles of thepresent disclosure may also be embodied as a software package installedon a hardware device.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to output to distinct, specifically programmedgraphical user interface implementations of the present disclosure(e.g., a desktop, a web app., etc.). In various implementations of thepresent disclosure, a final output may be displayed on a displayingscreen which may be, without limitation, a screen of a computer, ascreen of a mobile device, or the like. In various implementations, thedisplay may be a holographic display. In various implementations, thedisplay may be a transparent surface that may receive a visualprojection. Such projections may convey various forms of information,images, and/or objects. For example, such projections may be a visualoverlay for a mobile augmented reality (MAR) application.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to be utilized in various applications which mayinclude, but not limited to, gaming, mobile-device games, video chats,video conferences, live video streaming, video streaming and/oraugmented reality applications, mobile-device messenger applications,and others similarly suitable computer-device applications.

As used herein, the term “mobile electronic device,” or the like, mayrefer to any portable electronic device that may or may not be enabledwith location tracking functionality (e.g., MAC address, InternetProtocol (IP) address, or the like). For example, a mobile electronicdevice can include, but is not limited to, a mobile phone, PersonalDigital Assistant (PDA), Blackberry™, Pager, Smartphone, smart watch, orany other reasonable mobile electronic device.

As used herein, the terms “proximity detection,” “locating,” “locationdata,” “location information,” and “location tracking” refer to any formof location tracking technology or locating method that can be used toprovide a location of, for example, a particular computingdevice/system/platform of the present disclosure and/or any associatedcomputing devices, based at least in part on one or more of thefollowing techniques/devices, without limitation: accelerometer(s),gyroscope(s), Global Positioning Systems (GPS); GPS accessed usingBluetooth™; GPS accessed using any reasonable form of wireless and/ornon-wireless communication; WiFi™ server location data; Bluetooth™ basedlocation data; triangulation such as, but not limited to, network basedtriangulation, WiFi™ server information based triangulation, Bluetooth™server information based triangulation; Cell Identification basedtriangulation, Enhanced Cell Identification based triangulation,Uplink-Time difference of arrival (U-TDOA) based triangulation, Time ofarrival (TOA) based triangulation, Angle of arrival (AOA) basedtriangulation; techniques and systems using a geographic coordinatesystem such as, but not limited to, longitudinal and latitudinal based,geodesic height based, Cartesian coordinates based; Radio FrequencyIdentification such as, but not limited to, Long range RFID, Short rangeRFID; using any form of RFID tag such as, but not limited to active RFIDtags, passive RFID tags, battery assisted passive RFID tags; or anyother reasonable way to determine location. For ease, at times the abovevariations are not listed or are only partially listed; this is in noway meant to be a limitation.

As used herein, the terms “cloud,” “Internet cloud,” “cloud computing,”“cloud architecture,” and similar terms correspond to at least one ofthe following: (1) a large number of computers connected through areal-time communication network (e.g., Internet); (2) providing theability to run a program or application on many connected computers(e.g., physical machines, virtual machines (VMs)) at the same time; (3)network-based services, which appear to be provided by real serverhardware, and are in fact served up by virtual hardware (e.g., virtualservers), simulated by software running on one or more real machines(e.g., allowing to be moved around and scaled up (or down) on the flywithout affecting the end user).

The aforementioned examples are, of course, illustrative and notrestrictive.

As used herein, the term “user” shall have a meaning of at least oneuser. In some embodiments, the terms “user”, “subscriber”, “consumer”,or “customer” should be understood to refer to a user of an applicationor applications as described herein and/or a consumer of data suppliedby a data provider. By way of example, and not limitation, the terms“user” or “subscriber” can refer to a person who receives data providedby the data or service provider over the Internet in a browser session,or can refer to an automated software application which receives thedata and stores or processes the data.

At least some aspects of the present disclosure will now be describedwith reference to the following numbered clauses.

-   Clause 1. A method comprising:-   receiving, by a processor, a request from an application (app)    executing on a computing device of a user, the request being    transmitted in response to the user operating the app to a stage    where supplemental information is required to further operate one or    more functionalities of the app;-   generating, by the processor, the supplemental information based on    the request;-   segmenting, by the processor, the supplemental information into a    first part of the supplemental information and a second part of the    supplemental information;-   transmitting, by the processor, the first part of the supplemental    information to the computing device of the user via a first    communication channel to another app executing on the computing    device of the user;-   instructing, by the processor, the another app to allow the user to    utilize one or more graphical user interface (GUI) elements of a GUI    of the another app to transfer the first part of the supplemental    information to the app;-   receiving, by the processor, an indication of the transferring; and-   transmitting, by the processor based on the indication of the    transferring, the second part of the supplemental information to the    computing device of the user via a second communication channel so    as to provide the supplemental information to the app.-   Clause 2. The method of clause 1 or of any clause herein, wherein    the supplemental information comprises an authentication factor.-   Clause 3. The method of clause 2 of any clause herein, wherein the    authentication factor includes a one-time passcode one-time passcode    (OTP).-   Clause 4. The method of clauses 1-3 of any clause herein, wherein    the generating the supplemental information comprises:-   anonymizing, by the processor, the first part of the supplemental    information into unreadable format.-   Clause 5. The method of clauses 1-4 of any clause herein, wherein    the first part of the supplemental information and the second part    of the supplemental information are embedded in respective messages,    and the method further comprising:-   identifying, by the processor, a security token associated with the    user from a dataset configured for accounts of users associated with    the app, the security token being specified by the user at a prior    time; and-   generating, by the processor, the respective messages based on the    security token.-   Clause 6. The method of clauses 1-5 of any clause herein, wherein    the security token comprises one or more of: an image, a pass    phrase, a tone, a displaying color, a displaying motif, and a    displaying floating icon, the security token being displayed to the    user in association with the another app.-   Clause 7. The method of clauses 1-6 of any clause herein, wherein    the transferring the supplemental information comprises:-   populating the one or more GUI elements of the GUI of the app with    the supplemental information to enable the user to operate the one    or more functionalities of the app.-   Clause 8. The method of clauses 1-7 of any clause herein, wherein    the supplemental information is displayed at the another app as    anonymized data, the anonymized data comprising one or more of: a    string comprising one or more of randomized letters, numbers, and    symbols; an image; and text in a language foreign to the user, the    supplemental information not readable for the user and provided to    the app only upon transferring to the app.-   Clause 9. The method of clauses 1-8 of any clause herein, wherein a    message comprising at least part of the supplemental information is    customized for being displayed differently via one or more of: a    preview badge GUI of the another app, a push notification GUI of the    another app, a full-blown GUI of the another app, information of the    computing device, and information of an operating system of the    computing device.-   Clause 10. The method of clauses 1-9 of any clause herein, wherein    content of a message comprising at least part of the supplemental    information is customized based on one or more of:-   demographic data of the user; historical behavior data of the user;    demographic data of a group of users; and historical behavior data    of the group of users.-   Clause 11. A method comprising:-   receiving, by a server, a request from an application (app)    executing on a computing device of a user to a server, the request    being transmitted in response to the user operating the app to a    stage where supplemental information is required to further operate    one or more functionalities of the app;-   determining, by the server, the supplemental information based on    the request;-   anonymizing, by the server, a portion of the supplemental    information into unreadable format;-   transmitting, by the server, the unreadable portion of the    supplemental information in a message to a messaging app executing    on the computing device;-   detecting, by the server, that the user uses one or more graphical    user interface (GUI) elements of a GUI of the messaging app to    transfer the unreadable portion of the supplemental information to    the app; and-   causing, by the server, in response to the detecting, to provide a    remaining part of the supplemental information to the app.-   Clause 12. The method of clause 11 of any clause herein, further    comprising:-   generating, by the server, content of the message using a machine    learning model, the machine learning model trained using historical    completion rates and user demographic data associated with    historical message content, historical message formats, and    historical message channels.-   Clause 13. A server comprising:

one or more processors; and

a memory in communication with the one or more processors and storinginstructions that, when executed by the one or more processors, causethe server to:

-   receive a request from an application (app) executing on a computing    device of a user, the request being transmitted in response to the    user operating the app to a stage where supplemental information is    required to further operate one or more functionalities of the app;-   generate the supplemental information based on the request;-   segment the supplemental information into a first part of the    supplemental information and a second part of the supplemental    information;-   transmit the first part of the supplemental information to the    computing device of the user via a first communication channel to    another app executing on the computing device of the user;-   instruct the another app to allow the user to utilize one or more    graphical user interface (GUI) elements of a GUI of the another app    to transfer the first part of the supplemental information to the    app;-   receive an indication of the transferring; and-   transmit, based on the indication of the transferring, the second    part of the supplemental information to the computing device of the    user via a second communication channel so as to provide the    supplemental information to the app.-   Clause 14. The server of clause 13 of any clause herein, wherein the    supplemental information comprises an authentication factor.-   Clause 15. The server of clauses 13-14 of any clause herein, wherein    the authentication factor includes a one-time passcode (OTP).-   Clause 16. The server of clauses 13-15 of any clause herein, wherein    to generate the supplemental information comprises to:-   anonymize the first part of the supplemental information into    unreadable format.-   Clause 17. The server of clauses 13-16 of any clause herein, wherein    the first part of the supplemental information, and the instructions    further causing the server to:-   identify a security token associated with the user from a dataset    configured for accounts of users associated with the app, the    security token being specified by the user at a prior time; and-   generate the respective messages based on the security token.-   Clause 18. The server of clauses 13-17 of any clause herein, wherein    to transfer the supplemental information comprises to:-   populate the one or more GUI elements of the GUI of the app with the    supplemental information to enable the user to operate the one or    more functionalities of the app.-   Clause 19. The server of clauses 13-18 of any clause herein, wherein    the supplemental information is displayed at the another app as    anonymized data, the anonymized data comprising one or more of: a    string comprising one or more of randomized letters, numbers, and    symbols; an image; and text in a language foreign to the user, the    supplemental information not readable for the user and provided to    the app only upon transferring to the app.-   Clause 20. The server of clauses 13-19 of any clause herein, wherein    the message is customized for being displayed differently via one or    more of: a preview badge GUI of the another app, a push notification    GUI of the another app, a full-blown GUI of the another app,    information of the computing device, and information of an operating    system of the computing device.

1. A method comprising: receiving, by a processor via a firstcommunication channel, a request from a first application executing on acomputing device of a user, the request being transmitted in response tothe first application requiring authentication to enable user access;generating, by the processor, an authentication code based on therequest; segmenting, by the processor, the authentication code intofirst authentication data and second authentication data, wherein thefirst authentication data and the second authentication data areconfigured to be combined to recreate the authentication code;transmitting, by the processor, the first authentication data via asecond communication channel to a second application on the computingdevice; receiving, by the processor via the second communicationchannel, a receipt indication indicating that the second applicationreceived the first authentication data; transmitting, by the processorin response to the receipt indication, the second authentication datavia a third communication channel to a third application on thecomputing device; wherein the first communication channel, the secondcommunication channel and the third communication channel are distinct;wherein the first application, the second application and the thirdapplication are distinct; receiving, by the processor via the firstcommunication channel, at least one authentication message from thefirst application, wherein the at least one authentication messagecomprises a user-provided authentication code; determining, by theprocessor, that the user-provided authentication code matches theauthentication code; and instructing, by the processor, the firstapplication to authenticate the user so as to enable the user accessbased on the user-provided authentication code matching theauthentication code.
 2. The method of claim 1, wherein theauthentication code includes a one-time passcode (OTP).
 3. The method ofclaim 2, wherein the first authentication data comprises a first set ofcharacters of the OTP, and the second authentication data comprises asecond set of characters of the OTP, and wherein the first set ofcharacters and the second set of characters together form theauthentication code.
 4. The method of claim 1, wherein the generatingthe authentication code comprises: anonymizing, by the processor, thefirst authentication data into unreadable format.
 5. The method of claim1, wherein the authentication code is configured to expire upon apredetermined interval of time elapsing.
 6. The method of claim 1,wherein the first authentication data comprises one or more of: animage, a pass phrase, a tone, a displaying color, a displaying motif,and a displaying floating icon, the security token being displayed tothe user in association with the second application.
 7. The method ofclaim 1, wherein the transferring the first authentication datacomprises: populating the one or more GUI elements of the GUI of thefirst application with the authentication code to enable the user tooperate the one or more functionalities of the app.
 8. The method ofclaim 1, wherein the authentication code is displayed at the secondapplication as anonymized data, the anonymized data comprising one ormore of: a string comprising one or more of randomized letters, numbers,and symbols; an image; and text in a language foreign to the user, theauthentication code not readable for the user and provided to the firstapplication only upon transferring to the app.
 9. The method of claim 1,wherein a message comprising at least part of the authentication code iscustomized for being displayed differently via one or more of: a previewbadge GUI of the second application, a push notification GUI of thesecond application, a full-blown GUI of the second application,information of the computing device, and information of an operatingsystem of the computing device.
 10. The method of claim 1, whereincontent of a message comprising at least part of the authentication codeis customized based on one or more of: demographic data of the user;historical behavior data of the user; demographic data of a group ofusers; and historical behavior data of the group of users.
 11. A systemcomprising: at least one processor in communication with at least onenon-transitory computer-readable medium having software instructionsstored thereon, wherein, upon execution of the software instructions,the at least one processor is configured to: receive, via a firstcommunication channel, a request from a first application executing on acomputing device of a user, the request being transmitted in response tothe first application requiring authentication to enable user access;generate an authentication code based on the request; segment theauthentication code into first authentication data and secondauthentication data, wherein the first authentication data and thesecond authentication data are configured to be combined to recreate theauthentication code; transmit the first authentication data via a secondcommunication channel to a second application on the computing device;receive, via the second communication channel, a receipt indicationindicating that the second application received the first authenticationdata; transmit, in response to the receipt indication, the secondauthentication data via a third communication channel to a thirdapplication on the computing device; wherein the first communicationchannel, the second communication channel and the third communicationchannel are distinct; wherein the first application, the secondapplication and the third application are distinct; receive, via thefirst communication channel, at least one authentication message fromthe first application, wherein the at least one authentication messagecomprises a user-provided authentication code; determine that theuser-provided authentication code matches the authentication code; andinstruct the first application to authenticate the user so as to enablethe user access based on the user-provided authentication code matchingthe authentication code.
 12. The system of claim 11, wherein theauthentication code includes a one-time passcode (OTP).
 13. The systemof claim 12, wherein the first authentication data comprises a first setof characters of the OTP, and the second authentication data comprises asecond set of characters of the OTP, and wherein the first set ofcharacters and the second set of characters together form theauthentication code.
 14. The system of claim 11, wherein the generatingthe authentication code comprises: anonymize the first authenticationdata into unreadable format.
 15. The system of claim 11, wherein theauthentication code is configured to expire upon a predeterminedinterval of time elapsing.
 16. The system of claim 11, wherein the firstauthentication data comprises one or more of: an image, a pass phrase, atone, a displaying color, a displaying motif, and a displaying floatingicon, the security token being displayed to the user in association withthe second application.
 17. The system of claim 11, wherein thetransferring the first authentication data comprises: populating the oneor more GUI elements of the GUI of the first application with theauthentication code to enable the user to operate the one or morefunctionalities of the app.
 18. The system of claim 11, wherein theauthentication code is displayed at the second application as anonymizeddata, the anonymized data comprising one or more of: a string comprisingone or more of randomized letters, numbers, and symbols; an image; andtext in a language foreign to the user, the authentication code notreadable for the user and provided to the first application only upontransferring to the app.
 19. The system of claim 11, wherein a messagecomprising at least part of the authentication code is customized forbeing displayed differently via one or more of: a preview badge GUI ofthe second application, a push notification GUI of the secondapplication, a full-blown GUI of the second application, information ofthe computing device, and information of an operating system of thecomputing device.
 20. The system of claim 11, wherein content of amessage comprising at least part of the authentication code iscustomized based on one or more of: demographic data of the user;historical behavior data of the user; demographic data of a group ofusers; and historical behavior data of the group of users.